For more information on user groups, see Security 

User groups are an optional structure that can be configured in any WorkflowFirst application. They consist of a group of users under a title. A user can exist in more than one group. For example you may have groups for: 

 • Different departments 

 • Different ranks in the company, such as managers, new employees, senior or junior workers. 

 • Special cross-cutting groups, such as the disaster recovery team.

Under the user group, the drilldown 'Governance' allows a user group to be assigned governance over multiple areas of the data model.

To configure this, find the User Group (under Settings, User Groups), and then click on 'Workflow Governance'. Click 'Create New' to add a new area that will be governed by this user. 

The path that is entered here is in an XPath format, similar to the way you might refer to folders on your desktop computer. This concept was first introduced in Links The path entered here, though, is quite simple to formulate.

The start of the path must always be a forward slash ('/'). The next part is the name of the view, or the top-level field in your data model.

The governance affects all areas of the data model underneath the specified path. So, for example, if you specify /Facility and there are drilldowns from that type for Documentation, then the governance will affect the Documentation as well as anything underneath that.

The path can also refer to specific records, rather than just general types. If the path contains a filter (known as a predicate ), the governance will apply for that record only. 

For example, the path can be: 

Team[Name=”Development”]/Log 

And this would make this user group only govern changes to the Log in the Development team, and not any other team. 

Note : The filter can only apply to a single record at present. 

 
Next is the Condition . The condition is an optional DbfScript expression that must return either true or false. If the condition is omitted, then the governance always applies. If the condition is specified, then the governance only applies if the condition expression evaluate to true.

The input to the expression is the record being changed. Therefore you may need to utilize the Exists function to determine if a specific field is present in the update before checking any values.

For example you may have a condition such as:

Exists(#input/Limit) 

...and this would check whether the Limit field was present in the update. You could also have something that checks for specific values or ranges: 

#input/Limit > 50000 
 
Each workflow governance applies to all types underneath that type in the hierarchy. However, if a condition is specified then it will only apply to the type at the path specified. 

The last option is 'Only For Member Initiated'. This specifies that this particular approval governance is only applied if the user initiating the action is a member of this group. You can use this, for example, to have the supervisor for a specific department require approval of all members of that group only. Other groups, though, will not be affected by that governance. 

Of course this will only enforce approval workflow if the user making the change is denied the approval exclusion permission, as discussed in the previous section.